Browser, method, and computer program product for managing documents

ABSTRACT

A browser, method and computer program product for managing documents. The browser can receive and process a request from an input device of a image processing device. Based on this processing, the browser can transmit information over a network to a document manager connected to the scanning device via the network. The document manager can be connected, for example, to application service providers that store documents or to servers that deliver documents, such as e-mail servers and fax servers. The browser can receive information from the document manager. The information exchanged between the browser and the document manger can include, but is not limited to, documents, requests to retrieve documents, requests to store documents, requests to retrieve destination information (e.g., e-mail addresses and fax numbers), and search criteria.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a divisional application of Ser. No.10/243,643 (“the parent application”) filed Sep. 16, 2002 (now pending)and claims priority to Provisional Application Ser. No. 60/374,811 filedApr. 24, 2002, the entire contents of which is hereby incorporated byreference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention is directed to browsers used in systems formanaging documents or files. More particularly, the present inventionallows a multi function device to interact with another device connectedto the multi function device via a network.

2. Discussion of the Background

Browsers are already known. For example, Netscape's Communicator™ andMicrosoft's Internet Explorer™ are known World Wide Web browsers thatallow personal computers to interact with a Web server. Typically, a Webbrowser contacts a Web server and transmits a request for information.The Web server locates and then transmits the information to the Webbrowser, which displays the information. The information exchangedbetween the Web server and the Web browser can be in Hypertext MarkupLanguage (HTML).

While these conventional browsers work well for personal computers, theyare not designed to efficiently work with certain other devices. Inparticular, these conventional browsers may not work efficiently withmulti-function devices that incorporate scanners, copy machines,printers, and/or fax machines.

SUMMARY OF THE INVENTION

The present inventors have determined that there is a need for a browserthat can be efficiently incorporated in a device, such as amulti-function device (MFD), to allow a user to manage documents over anetwork. An MFD can incorporate a scanner, a copy machine, a printer, afax machine, a digital camera, other office devices, and combinationsthereof. One object of the present invention is to provide a browserthat allows the user of an MFD to transmit and receive documents,requests, information to and from a document manger connected to the MFDvia a network. The document manager can be a device connected toapplication service providers (ASPs) via a network and configured tomanage documents between the ASPs and the MFD.

Another object of the present invention is to provide a browser thatallows the user of an MFD to process a document and to e-mail, fax, orotherwise electronically deliver the processed document from the MFD. Inthis embodiment, the document manager is a scan server configured tomanage documents and destination information (e.g., e-mail addresses andfax numbers) between the MFD and various servers (e.g., e-mail serversand fax servers).

These and other objects can be achieved by providing a browserconfigured to receive a request from an input device of the scanningdevice (e.g., the touch buttons displayed on a screen). The browserprocesses the request and transmits information based on the requestover a network to the document manager connected to the canning devicevia the network. The browser is also configured to receive informationfrom the document manager. The browser can be configured to display theinformation received from the document manager on the display of theMFD. The request received by the browser can include, but is not limitedto, a request to retrieve a document, a request to store a document,and/or a request to retrieve destination information (e.g., e-mailaddresses and fax numbers). The browser can transmit information to thedocument manager. That transmitted information includes, but is notlimited to, login information related to the identity of the user ofMFD, a search criterion for searching a document, a document (e.g.,scanned by the MFD), and/or a search criterion for searching adestination information. The browser can receive information from thedocument manager. For example, the browser can receive a retrieveddocument, information about the storage of the document, and/ordestination information. The browser can transmit data using an HTTPprotocol and an XML format.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the invention and many of the attendantadvantages thereof will be readily obtained as the same becomes betterunderstood by reference to the following detailed description whenconsidered in connection with the accompanying drawings, wherein:

FIG. 1 is a block diagram showing an overall system configurationaccording to a preferred embodiment of the present invention;

FIG. 2 is a block diagram illustrating a browser according to thepreferred embodiment shown in FIG. 1;

FIG. 3 is a block diagram showing an overall system configurationaccording to another preferred embodiment of the present invention;

FIG. 4 is a block diagram illustrating a browser according to thepreferred embodiment shown in FIG. 3;

FIGS. 5-8 show examples of menus displayed on a display screen of ascanning device according to a preferred embodiment;

FIGS. 9-10 show flowcharts of a method of managing documents from thescanning device according to one embodiment of the present invention;

FIG. 11 is a block diagram illustrating a scanning device according toone embodiment of the present invention;

FIG. 12 is a schematic representation of a scanning device according toone embodiment of the present invention; and

FIGS. 13-14 show flowcharts of a method of managing documents with anMFD browser according to one embodiment of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Referring now to the drawings, wherein like reference numerals designateidentical or corresponding parts throughout the several views, FIGS. 1and 3 are block diagrams of systems 1 and 5 for managing documentsaccording to the present invention. The systems 1 and 5 include anetwork 100 that interconnects at least one user device 20, butpreferably a plurality of user devices 10, 20, 30 to a document manager40. The user devices 10-30 include a browser (shown in FIGS. 2 and 4)configured to exchange data between the user devices 10-30 and thedocument manager 40.

In the preferred embodiment shown in FIG. 1, the system 1 also includesa network 102 that interconnects at least one, but preferably aplurality of application service providers (ASPs) 51, 61, 71, 81, to thedocument manager 40. An ASP is an entity, typically a company, thatoffers users (individual customers, companies, corporations,organizations, etc . . . ) access over a network, such as the Internet,to applications and related services that would otherwise have to belocated on the user's local computer. For example, ASPs can providesearchable databases of legal, medical, financial, educational,scientific, or marketing documents. A system similar to the one shown inFIG. 1 is described in detail in Ser. Nos. 09/684,965, and 09/795,438the entire contents of which are hereby incorporated by reference.

The user devices 10, 20 and 30 are remote with respect to the documentmanager 40. The networks 100 and 102 are preferably the Internet in thisembodiment, but can also be a local area network, a wide area network,any type of network such as an intranet, an extranet, or a combinationthereof. An extranet may be used to provide controlled access toexternal users, for example through the Internet. How the user devices10, 20 and 30 and the document manager 40 can be connected to theInternet 100 and 102 is well-known in the art and is explained forexample, in part 38 of “How Computers Work”, by Ron White, QueCorporation, pps. 340-349, September, 1999, ISBN: 0-7897-2112-0, theentire content of this book being hereby incorporated by reference.Other communications links for the networks 100 and 102, such as avirtual private network, or a wireless link, may be used as well.

The user devices 10, 20 and 30 include an image processing apparatus,such as a multi-function device, or “MFD.” An MFD can incorporate ascanner, a copy machine, a printer, a fax machine, a digital camera,other office devices, and combinations thereof. Various types of MFDsare commonly known in the art and share common features and hardwarewith the MFDs of the present invention. In one embodiment of the presentinvention, the MFD is a portable device, such as a digital camera,connectable to the Internet via wireless connection/network. Such an MFDcombines digital imaging with the power of the Internet so that one cancapture still, sounds or videos and share them wirelessly from variouslocations. The MFD can create web pages, send and receive e-mails withattachments, edit images, FTP files, surf the Internet, and send a fax.In another embodiment, the MFD is a multiple scanner, photocopier andprinter, as described in more detail below with corresponding FIGS.11-12. The MFDs 10-30 can be directly connected to the network 100. Thebrowsers 25 (shown in FIGS. 2 and 4) of MFDs 10-30 can exchangeinformation with the document manager 40 via the network 100, so as tobenefit from a number of services provided by the document manager 40.

For example, in the embodiment shown in FIG. 1, the browser 25 (FIG. 2)of the MFD 20 can provide the document manager 40 with a request forstoring at an ASP 51 a document scanned or an image processed by the MFD20. The browser 25 can provide the document manager 40 with jobinformation related to a job performed on a document or image by the MFD20. For example, the browser 25 can transmit to the document manager 40job information such as the number of pages scanned or printed, thenumber of documents scanned or printed, the number of digital imagestaken, the scanning/printing resolution (e.g., 200, 400, 600, 1200 dotper inch), the scan/print mode (Text, Gray, Scale, Photo, Text&Photo),the size of the paper for the document/image, the color selection(selected by the operator and/or automatically selected by the MFP 20),the compression ratio of the image data (e.g., fine, normal, economy),the image data format, i.e., the compression method of the image data(e.g., Bitmap, PDF, JPEG, JPEG2000). Using this job information, thedocument manager 40 can update a job log for that user. The documentmanager 40 can generate billing information based on the job performed.The browser 25 can also provide the document manager 40 with otherinformation such as user I.D.s, passwords, the name of the personscanning or printing the document, the name of the author of thedocument, the date and time of the scanning or printing, the version ofthe document, the serial number, model name and/or location of the MFD20.

FIG. 2 illustrates an MFD 20's browser 25 configured to exchangeinformation between the MFD 20 and the document manager 40 according tothe first embodiment of the present invention. FIG. 2 shows the softwarecomponents in the MFD-document manager system; the hardware elements arenot shown in FIG. 2. The document manager 40 shown in FIG. 2 includes auser interaction device 261 configured to exchange data with the browser25 of the MFD 20 so that the user of the MFD 20 can benefit from anumber of services provided by the document manager 40. The informationexchanged between the browser 25 and the document manager 40 includes,but is not limited to, documents processed (e.g., scanned) by the MFD20, documents stored at the ASPs, job information related to the jobperformed by the MFD 20, login information related to the identity ofthe user of the MFD 20, criteria for searching documents at the ASPs,requests to search documents, request to store documents, other requestsrelated to the management of documents, e-mail addresses, fax numbers,etc.

In one embodiment, the user of the MFD 20 can access the documentmanager 40 by providing login information, for example by transmitting auser-name and a password, which can be verified by user interactiondevice 261. In this case, the browser 25 is configured to transmit thatlogin information to the user interaction device 261 of the documentmanager 40. The user interaction device 261 can verify the user'sauthorization by comparing the login information to information storedin a storage device at the document manager 40. The user interaction 261can also transmit to the MFD 20 a confirmation of the user'sauthorization. In this case, the browser 25 is configured to receivethis confirmation from the document manager 40.

The browser 25 can also be configured to transmit job information to theuser interaction device 261. The job information relates to the jobperformed by the MFD 20 and can include the scanning parameters (e.g.,the scanning resolution, the compression ratio, the image data format,the color selection, the size of paper), the number of pages scanned orprinted, the number of documents scanned or printed. The documentmanager 40 can include a charge engine 266 configured to generatebilling information based on the job information. For example, thecharge engine 266 can compute bills by multiplying the values of certainscanning parameters (part of the job information) by charges determinedfor each parameter. After computing these billable items, the chargeengine 266 can transmit the billing information and/or the bills to theASP 51. The browser 25 is configured to transmit this job informationfrom the MFD 20 to the document manager 40. The charge engine 266 canalso receive bills from the ASPs 51-81 and generate other bills to betransmitted to the MFD 20. In this case, the browser 25 is configured toreceive the bills from the document manager 40 at the MFD 20.

The document management 40 can also include a search engine 271configured to search and access ASPs 51-81 based on data, or searchcriteria, input from the user of the MFD 20. In this case, the browser25 is configured to transmit the search criteria to the document manager40. The browser 25 is also configured to receive from the documentmanager 40 the results of the search, e.g., documents retrieved form theASPs. The document manager 40 can also include a format standardizingdevice 276 configured to standardize the formats of the documentsretrieved from various ASPs and the MFD 20. For example, the formatstandardizing device 276 can re-format the documents so that they may beaccessed using a single GUI. In this case, the browser 25 can beconfigured to transmit the documents from the MFD 20 to the documentmanager 40 with a request to standardize the documents. In anotherembodiment, the document manager 40 includes a consulting device 281configured to provide the user of the MFD 20 consulting servicesregarding the services provided by the document manager 40. In thiscase, the browser 25 is configured to transmit requests for informationto the document manager 40 from the MFD 20. The browser 25 is alsoconfigured to receive from the document manager 40 the requestedinformation.

As shown in FIG. 2, the MFD 20 includes an engine control service (ECS)200 that controls for example the scanning engine of the MFD 20. Amemory control service (MCS) 205 controls access to the memory 210 ofthe MFD 20. An operation panel control service (OCS) 215 generatesdisplays for the LCD of the MFD 20. For example, the OCS 215 cangenerate conventional menus for MFD operation and the menus shown inFIGS. 5-8. A system control service (SCS) 225 controls and/or monitorssensors within the MFD 20. For example, the SCS 225 controls the touchscreen sensors, paper jam sensors and scanning operation sensors.Accordingly, the SCS 225 can manage the status of the MFD 20 based onthe information from the sensors. A network control service (NCS) 220controls communication between the browser 25 and the scan server 40.Optionally, a secure socket layer (SSL) 230 provides added security forcommunications between the NCS 220 and the browser 25. A command inputservice (CIS) 240 processes input information, e.g., from the LCD touchpanel and a key pad of the MFD 20. A user of the MFD can enterinformation and commands using the LCD touch panel and the key pad. TheCIS 240 can process such information and commands entered by a user(e.g., forwarded to the CIS 240 by the SCS 225). The CIS 240 cangenerate a command (e.g., a display command) based on such processingand transmit the command to other components of the MFD (e.g., to theOCS 215 to display a graphic on the LCD). The CIS 240 can also exchangeinformation and commands with the NCS 220 for processing with thebrowser 25 in connection with the document manger 40.

Conventional MFDs include ECSs, MCSs, OCSs, NCSs, SCSs, and CISs, whichare firmware for implementing and controlling each hardware component ofthe MFD. In the present invention, however, the NCS 220 is configured tocommunicate with the browser 25. For instance, the NCS 220 hasadditional capabilities for communicating using the HTTP protocol. TheNCS 220 is also configured to communicate with the document manager 40so that the NCS 220 exchanges data between the browser 25 and thedocument manager 40. For example, The NCS 220 can transmit to thedocument manager 40 a document storage request and/or a document searchrequest and can receive from the document manager 40 storage informationand/or a retrieved document.

The browser 25 includes an HTTP command processor 235 that communicateswith the network control service (NCS) 220 of the MFD 20. For example, arequest for a document entered by the user via the MFD keyboard, or arequest for displaying information on the LCD, such as FIGS. 5-8, can bepassed from the NCS 220 to the browser 25 by the HTTP command processor235. The HTTP command processor 235 can exchange data in the HTML formatwith the browser's HTML parser 250, and can exchange data in the XMLformat with the XML parser 255. The parsers 250 and 255 can check thedata from the HTTP command processor 235 for syntax, process the datafor HTTP command processor 235. The present invention can includeconventional parsers, which are usually part of a compiler.

The HTTP command processor 235 can be provided with a program code forimplementing a specific application, such as, user authenticationprocessing which can be implemented with the directory service of thedocument manager 40. The HTTP command processor 235 can processinformation based on definitions of the specific application. Forexample, the HTTP command processor 235 can process information providedby the user, such as User Name or Password, and generate an HTTP requestbased on this processing for the document manager 40. The HTTP commandprocessor 235 can process information provided by the MFD components,such as job information (number of documents processed, scan/printparameters, date and time of job, user ID, etc . . . ) and generate anHTTP request based on this processing for the document manager 40. TheHTTP command processor 235 can transmit such HTTP requests to the NCS220 to be transmitted to the document manager 40.

The HTTP command processor 235 can also process information receivedfrom the document manager 40 (via the NCS 220). For example, the HTTPcommand processor 235 can receive an HTTP response generated by thedocument manager 40 which includes parameters for operating the MFD. Theparameters can be stored for example in the user interaction device 261of the document manager 40. The parameters can include a specific userID as a result of the user authentication processing. Furthermore, theparameters can include destination computer to receive job information,destination folder on the networked computer's hard drive for thedocuments processed by the MFD, restrictions for the MFD functionsdepending on user authentication, scanning/printing job parameters forthe specific user ID, such as default size of papers, scanningresolution setting, condition of the document feeder, or department codefor billing the operation. The HTTP command processor 235 can processthis information and generate commands to control the MFD in accordancewith the information, e.g., can request the MFD to scan/print accordingto the job parameters for the specific user ID. As another example, theHTTP command processor 235 can generate a graphic drawing command forthe LCD panel. The HTTP command processor 235 can transmit the commandsto the appropriate MFD firmware (e.g., the OCS 215) so as to beexecuted. For example, the OCS 215 can receive the graphic drawingcommand and execute it by displaying a graphic (e.g., FIGS. 3-6) on theLCD panel.

FIGS. 13 and 14 show flowcharts of a method of managing documents withthe MFD browser 25. More specifically, FIG. 13 shows an HTTP requesthandling process flow, and FIG. 14 shows an HTTP response handlingprocess flow. Turning to FIG. 13, at step 3100 a user operates the MFDpanel, for example selects a button on the MFD's LCD touch panel. Atstep 3150, the SCS 225 detects the panel operation, e.g. a location ofthe selected button, and transmits panel operation information to theCIS 240. At step 3200, the CIS 240 interprets the panel operationinformation and generates a command. This interpretation and generatingof the command can be based on a definition described in a predeterminedprogram code. The predetermined program code can be provided forimplementing the specific application executed by the MFD 20 and theserver 40. For example, the specific application may include a userauthentication using the document manager 40, or scan-to-eMail serviceswith MFD 20 and document manager 40. The predetermined program code forthe specific application can be provided in an IC Card, or other medium,for the MFD.

At step 3250, the CIS 240 transmits the command to the HTTP commandprocessor 235. At step 3300, the HTTP command processor 235 generates anHTTP requests composed in the HTML language and/or the XML languagebased on the command. At step 3350, the HTTP command processor 235transmits the HTTP request to the NCS 220. Optionally, the HTTP commandprocessor 235 transmits the HTTP request to the SSL 230, i.e., the HTTPrequest is sent using HTTPS protocol or Secure Sockets Layer over HTTP,based on the definition of the predetermined program code for thespecific application. At step 3400, the NCS 220 transmits the HTTPrequest to the document manager 40.

Turning to FIG. 14, at step 4100, the document manager 40 generates anHTTP response based on the processing defined by the specificapplication. For example, the authentication result information can beincluded in the HTTP response. The document manager 40 transmits thisHTTP response to the NCS 220. In this process, the HTTP response can besent using HTTPS protocol depending on the definition of thepredetermined program code for the specific application. At step 4150,the NCS 220 receives the HTTP response and transmits it to the HTTPcommand processor 235. At step 4200, the HTTP command processor 235receives the HTTP response from the NCS 220 and transmits it to the HTMLparser 250 and/or to the XML parser 255. At step 4300, the XML parser255 processes the HTTP response for the HTTP command processor 235. Atstep 4400, the HTML parser processes the HTTP response for the HTTPcommand processor 235. At step 4450 the HTTP command processor 235generates a command based on this processing, and transmits the commandto one of the MFD components, e.g. the CIS 240. At step 4500, the CIS240 generates a display request based on the command and transmits thedisplay request to the OCS 215. At step 4600, the OCS 215 processes thedisplay request. For example, at step 4700, the LCD panel displaysgraphics, such as the menus shown in FIGS. 3-6.

FIG. 3 is a block diagram of a system 5 for scanning and managingdocuments according to another preferred embodiment of the presentinvention. In particular, the system 5 allows a user to process adocument (e.g. scanning, capturing an image) and to e-mail and/or faxthe document from the MFD. The system 5 includes a network 100 thatinterconnects at least one, but preferably a plurality of scanningdevices 10-30, to a document manager 40. In this embodiment, thedocument manager 40 is a scan server 40. The network 100 preferably usesTCP/IP (Transmission Control Protocol/Internet Protocol) because thisprotocol is commonly used, but other protocols are possible. The network100 can be a local area network, a wide area network, any type ofnetwork such as an intranet, an extranet, or a combination thereof.Other communications links for the network 100, such as a virtualprivate network, or a wireless link, may be used as well.

As shown in FIG. 3, the scanning devices 10-30 can be MFDs. The server40 is connected to a directory server 60 (or “address book server” or“global directory”). The directory server 60 can include informationsuch as the names, addresses, e-mail addresses, phone/fax numbers, othertypes of destination information, and authorization of individuals.Other information can be included in the directory server 60. Examplesof directory servers 60 compatible with the present invention include,but are not limited to, Lotus Notes™, Microsoft Exchange™, and LDAP(“Lightweight Directory Access Protocol”) enabled directory servers.LDAP is a software protocol that enables a user to locate organizations,individuals, files, devices in a network. The scan server 40 can also beconnected to a network domain controller 50 that controls authenticationof the MFD users.

The system 5 provides access to the users of the MFDs 10-30 of theinformation stored at the directory server 60 via the scan server 40.Accordingly, a user can create a document (e.g., scan, capture image) atthe MFD 20, and request a search of the company's global directorystored at the directory server 60. The scan server 40 can pass thesearch request to the directory server 60 and can receive the searchresults (e.g., e-mail addresses and/or fax numbers) from the directoryserver 60. The scan server 40 can pass the search results to the MFD 20,which can temporarily store and display them. In a preferred embodiment,the stored search results are erased automatically from the MFD afterthe job of the MFD is completed, or after a time period (e.g., twominutes) that can be set by the administrator of the system. The usercan select e-mail addresses and fax numbers from the displayed searchresults and request that the document be e-mailed and/or faxed to theselected addresses. Alternatively, the user can enter the addresses andnumbers, or can select addresses and numbers from a local directorystored in the scanning devices 10-30. The local directory can be updatedautomatically or periodically after the directory server is updated.

The scan server 40 receives the document and the selectedaddresses/numbers from the MFD 20 and routes the scanned document to theappropriate server. For example, if the user requests the document to bee-mailed, the scan server 40 routes the document to an e-mail server 70.If the user requests the document to be faxed, the scan server 40 routesthe document to a fax server 80. The scan server 40 can also route thedocument to other applications 90, which may, for example, convert adocument from one format (e.g., TIFF, “Tag Image File Format”) toanother (PDF, “Portable Document Format”).

In the present embodiment, the Scan Server 40 can be configured to actas an intermediate agent between a plurality of computerized services(e.g., provided by devices 50, 60, 70, 80, and 90) so that the MFDs canperform a plurality of functions in a same scanning job. The Scan Server40 can be configured to display the plurality of services based on arequest from the browser 25. The MFD can display screens prompting theentry of a plurality of parameters such as e-mail addresses, fax numbersand billing codes, on the LCD panel based on the communication betweenthe Browser 25 and the Scan Server 40. The MFD can then transmit thedocument to a plurality of servers, e.g., servers 70, 80, and 90.

In a preferred embodiment, the browsers 25 of the MFDs 10-30 and thescan server 40 exchange data using the protocol HTTP (“HypertextTransfer Protocol”) or HTTPS (HTTP over Secure Socket Layer) over thenetwork 100. Other protocols can equivalently be used with the presentinvention. Preferably, the browsers 25 of the MFDs 10-30 and the scanserver 40 exchange data using the format XML (“Extensible MarkupLanguage”). Other formats, such as HTML, can equivalently be used withthe present invention. In a preferred embodiment, the e-mail server 70is incorporated into the scan server 40. E-mail server 70 can include,but is not limited to, Lotus Notes™ e-mail server, Microsoft Exchange™e-mail server, and SMTP (“Simple Mail Transfer Protocol”) e-mailservers. In a preferred embodiment, the fax server 80 is the Captaris'RightFax™ server.

The system 5 provides three levels of user authentication. At a firstauthentication level, no user authentication is performed. Under thisfirst level, any user can use the MFDs 10-30 to scan, copy, print,access the global directory server 60 to e-mail and fax documents.

At the second authentication level, the user is domain authenticated bythe network domain controller 50. Under this second level, the userenters login information, such as a login name and a password. Thislogin information is transmitted to the scan server 40 via the network100 by the MFD's browser 25. The scan server 40 passes the logininformation to the network domain controller that confirms (or not) theuser's domain authentication. The confirmation is passed to the browsersof the MFDs 10-30 via the scan server 40. If the user is domainauthenticated, the user can use the MFD and its functions. In oneembodiment, the system 5 can be configured so that certain functions ofthe MFDs 10-30, such as copying and direct e-mail and faxing (withoutaccess to the global directory server 60), be accessible to a user whois not domain authenticated. Under this embodiment, however, the systembars the non-authenticated user from using other functions, includingaccess to the global directory server 60. Under another embodiment, thesystem bars the non-authenticated user from using all functions providedby the MFDs 10-30.

At the third authentication level, the user is authenticated by thedirectory server 60. Under this third level, the directory server 60 cancontrol what portions (if any) of the directory, to which the user canhave access. For example, employees of a particular division of thecompany (e.g., human resources, legal, etc . . . ) may have access tothe portion of the directory that corresponds to that division only.More sensitive information can thus be protected and accessible only bycertain individuals within the company. This third authentication levelcan be, but need not be, in addition to the second level.

Under the second and third authentication levels, the system can createa user profile such that upon authentication, the system provides accessto the user only for certain functions that correspond to the userprofile. Under this embodiment, different authenticated users can havedifferent user profiles and thus have access to different functions. Theadministrator can control the user profiles.

In a preferred embodiment, the scan server 40 can include a profilerthat sets a specific MFD profile for a specific MFD. The administratorof the system 5 can create, change and maintain profiles via a profilescreen on the scan server 40. The profile can include an identificationfor the MFD, such as a serial number, and various parameters (computernetwork-name, machine location, etc . . . ) used to configure theexchange of information between the scan server 40 and the browsers ofthe MFDs 10-30. These parameters can relate to the authentication schemeused for each MFD, to the data format/protocols used, to the e-mailserver 70, to the fax server 80, and/or to the directory server 60. Theprofile can also include the time period during which the search resultsfrom the directory server are stored at the scanning device before beingerased.

FIG. 4 illustrates an MFD 20's browser 25 configured to exchangeinformation between the MFD 20 and the scan server 40 according to apreferred embodiment of the present invention. FIG. 4 shows the softwarecomponents in the MFD-server system; the hardware elements are not shownin FIG. 4. The scan server 40 shown in FIG. 4. includes anauthentication device 260 configured to perform the authenticationfunctions discussed above. The scan server 40 also includes anadministration device 265 that allows the system administrator toadminister the system 5. For example, the administrator of the systemcan access the profiler 280 via the administration device 265 to setprofiles for the MFDs 10-30 connected to the scan server 40. The scanserver 40 also includes a directory gateway 270 configured tocommunicate with the directory server 60. The scan server 40 alsoincludes a document router 275 configured to route the documentsreceived from the MFDs to the appropriate server 70, 80 or 90.

As shown in FIG. 4, the MFD 20 includes the same components as thoseshown in FIG. 2 and already discussed above. In this embodiment,however, the NCS 220 is configured to communicate with the server 40 sothat the NCS 220 exchanges data between the browser 25 and the server40. For example, The NCS 220 can transmit to the server 40 a request foran e-mail address and can receive from the server 40 a selected e-mailaddress, or the NCS 220 can transmit to the server 40 login informationand can receive a user authentication confirmation from the server 40(and from the directory server 60) during an authentication process.

In a preferred embodiment, the MFDs 10-30 provide interactive menusbased on information inputted by the operator of the MFD, so as to allowthe operator to conveniently take advantage of the services provided bythe system 5. Examples of menus displayed on touch sensitive LCDs of theMFDs are shown in FIGS. 5-8. FIG. 5 illustrates a screen 300 thatintroduces a preferred embodiment of the present invention to the userand that provides touch sensitive buttons, for example buttons 305-325.Upon touching the button 305, the MFD displays a screen (not shown) thatprompts the user to enter login information. The browser 25 receives thelogin information along with a request to transmit this information tothe scan server 40. Once the browser 25 processes this request, thebrowser 25 can transmit the login information to the scan server 40.

Upon touching the button 310, the MFD displays a screen (such as screen500 shown in FIG. 7) which permits the user to fax a document. Upontouching the button 315, the MFD displays a screen (such as screen 600shown in FIG. 8) which permits the user to e-mail a document. Upontouching the button 320, the MFD displays a screen (such as screen 400shown in FIG. 6) which prompts the user to enter settings for scanning adocument. Upon touching the button 325, the MFD displays a screen (notshown) which displays a job log, which keeps track of previous jobsperformed by the MFD. The screen 300 includes a system display portion330 that displays system messages, such as the time and date, errormessages, or instructions to the user. The screen 300 includes a maindisplay portion 335 that displays information for the user. Screen 300can include other display portions. The screen 300 also includes buttons340, which permit the user to scroll through the display shown in themain display portion 335.

FIG. 6 illustrates a screen 400 with touch sensitive buttons used to setthe scanning parameters. The screen 400 can include a default button 405to request the MFD to scan the document using its default scanningparameters (e.g., 200 dpi). The default parameters may be displayedbelow the button 405. Upon being touched, a “Fine Scan” button 410requests the MFD to scan the document using finer scanning parameters(e.g., 300 dpi) than the default parameters. These finer scanningparameters can be displayed below the button 410. Upon being touched, a“Super Scan” button 415 requests the MFD to scan the document using evenfiner scanning parameters (e.g., 400 dpi) than the fine parameters.These even finer scanning parameters can be displayed below the button415.

The screen 400 can also include a “Create PDF” button 430 that requests,upon touching, the document to be converted to the PDF format. Thisconversion can take place at the MFD, at the scan server, or at aconversion server 90. In a preferred embodiment, the browser 25transmits the document to the scan server 40 in the TIFF format alongwith the request to convert to the PDF format. The scan server 40 thensends the document to the conversion server 90 to be converted into thePDF format.

If the user does not want the document converted to the PDF format, theuser can touch a “Keep TIFF” button 435 to request that the document bekept in the TIFF format. In this case, the browser 25 transmits thedocument in the TIFF format to the scan server 40 along with a requestnot to convert the document to another format. Alternatively, thebrowser 25 can transmit the document to the scan server 40 in any formatand without any request. In this case, the scan server 40 can beconfigured to keep the document in whatever format it is received.

The user can also touch the “Scan Size” button 440 to set the size ofthe document to be scanned. The user can also select a single sided scanby touching the “Single-Sided” button 420, or select a double sided scanby touching the “Double-Sided” button 425. Once the user has selectedall the scanning parameters, the user can save his selection by touchingthe “Save” button 445. Alternatively, if the user wants to return to theprevious screen 300, the user can touch the “Exit” button 450.

FIGS. 7 and 8 illustrate screens 500 and 600 used to request faxing ande-mailing documents, respectively. Text (e.g., for a fax note or ane-mail message) can be entered via the LCD using a touch sensitivekeyboard (not shown) displayed on the LCD. Upon touching the “Enter FaxNote” button 510, the MFD displays a screen that permits the user toenter a fax note along with the document to be faxed. The fax note canbe displayed in portion 555 of the screen 500. Upon touching the “EnterFax Number” button 520, the MFD displays a screen that permits the userto enter the fax number to which the document is to be faxed. The usercan manually enter the fax number if the user already knows the faxnumber. If the user does not already know the fax number, the user canlook it up in the global directory, as discussed next.

Upon touching the “Lookup Fax Number” button 525, the MFD displays ascreen that prompts the user to enter the name(s) of a recipient(s), orthe name of a group of recipients (e.g., “marketing,” “management,”“security,” “legal department,” “blue division,” “softball team,” etc .. . ). Search criteria other than names can be used. The MFD can sendthe names or other search criteria to the scan server 40, which passesthe information to the directory server 60. The directory server 60 thenreturns the fax numbers for the names entered by the user to the scanserver 40, which passes the fax numbers to the MFD for displaying on theportion 545 of the screen 500. The display portions 550 can be touchedto select (e.g. by highlighting) fax numbers listed on the portion 545.The selected fax numbers can be removed from the recipients' list bytouching the “Remove Fax Number” button 530. Upon touching the “OK”button 535, the information received via the screen 500 can be processedby the MFD to fax the document. The user can return to the previousscreen by touching the “Cancel” button 540. Upon touching the “BillingCode” button 515, the MFD displays a bill management screen (not shown)to receive billing information. For example, the bill management screenwould prompt the user to enter a department code representing thedepartment to which the user belongs. With this feature, the MFD caneither locally process the billing information and/or transmit thebilling information to the server 40 for centralized processing.

Turning to the screen 600 illustrated in FIG. 8, upon touching the“Enter Subject” button 605, the MFD displays a screen that permits theuser to enter a subject for the document to be e-mailed. This subjectcan be displayed in portion 655 of the screen 600. Upon touching the“Enter E-mail Message” button 610, the MFD displays a screen thatpermits the user to enter an e-mail message along with the document tobe e-mailed. Upon touching the “Document Name” button 615, the MFDdisplays a screen that permits the user to enter the name of thedocument to be e-mailed. Upon touching the “Enter E-mail Address” button620, the MFD displays a screen that permits the user to enter the e-mailaddress to which the document is to be e-mailed. The user can manuallyenter the e-mail address if the user already knows the e-mail address.If the user does not already know the e-mail address, the user can lookit up in the global directory, as discussed next.

Upon touching the “Lookup E-mail Address” button 625, the MFD displays ascreen that prompts the user to enter the name(s) of a recipient(s), orthe name of a group of recipients (e.g., “marketing,” “management,”“security,” “legal department,” “blue division,” “softball team,” etc .. . ). Search criteria other than names can be used. The browser 25 canreceive the entered names or other search criteria and transmit them tothe scan server 40, which passes the information to the directory server60. The directory server 60 then returns the e-mail addresses for thenames entered by the user to the scan server 40, which passes the e-mailaddresses to the MFD 20. The browser 25 receives the e-mail addressesfrom the scan server 40 and can display them on the portion 645 of thescreen 600. The display portions 650 can be touched to select (e.g. byhighlighting) the e-mail addresses listed on the portion 645. Theselected e-mail addresses can be removed from the recipients' list bytouching the “Remove E-mail Address” button 630. Upon touching the “OK”button 635, the information received via the screen 600 can be receivedand processed by the browser 25. In particular, the browser 25 cantransmit to the scan server 40 the document to be e-mailed along with arequest to e-mail the document to the e-mail addresses selected orentered by the user. The scan server 40 processes this information androutes the document to the e-mail server for e-mailing. The user canreturn to the previous screen by touching the “Cancel” button 640.

FIG. 9 illustrates a method of authenticating a user according to oneembodiment of the present invention as performed by the MFDs 10-30 andits browser 25. At step 705, the MFD inquires whether a command isreceived from the user to display a login screen. For example, the usercan press a login button on the LCD of the MFD 20, such as the “Log in”button 305 of screen 300 shown in FIG. 3. At step 710, the MFD 20displays the login screen if the command is received. At step 715, thebrowser 25 inquires whether the login information is received from theuser. For example, the browser 25 can inquire whether the user entered auser name, a password, and a domain name. Once the browser 25 hasreceived the login information, the browser 25 transmits the logininformation to the scan server 40 at step 720. The scan server 40 thensends the login information to the network domain controller 50. Thedomain controller 50 verifies the login information and sends aauthentication confirmation to the scan server 40 that forwards theconfirmation to the MFD 20. At step 725, the browser 25 inquires whetherthe authentication confirmation is received from the scan server 40.Once the MFD 20 receives the user authentication, the MFD 20 downloadsfrom the scan server 40 a user's home page for display at step 730. Forexample, the user's home page can include a start page, such as the oneshown in FIG. 3. The user home page can be a kind of default (portal)page initially displayed after authentication. In the present invention,this home page can be generated based on the result of userauthentication. In a preferred embodiment, the user home page can beprovided with a “Help” button, and/or a “About” button to provideinstruction and information for using system of the present invention.

FIG. 10 illustrates a method of accessing the global directory accordingto one embodiment of the present invention, as performed by the MFD 20and its browser 25. The global directory can be accessed for the purposeof performing a search, such as a fax number search and/or an e-mailaddress search. At step 805, the MFD 20 inquires whether the userrequested to search the global directory. For example, the user canrequest such a search by pressing the lookup buttons 525 and 625 shownin FIGS. 7-8. If such a search is requested, the MFD 20 displays ascreen at step 810 that prompts the user to enter a search string, forexample a string of at least two characters. At step 815, the browser 25inquires whether the search string has been entered. Once the browser 25has received the search string, the browser 25 transmits the searchstring to the scan server 40 at step 820. The scan server 40 forwardsthe search string to the directory server 60, which performs the searchand transmits the search results to the scan server 40. The scan server40 transmits the search results to the MFD 20. At step 825, the MFD 20inquires whether the search results have been received from the scanserver 40. Once the browser 25 has received the search results, thebrowser can display the search results on the display of the NFD 20 atstep 830.

FIGS. 11-12 illustrate an example of the MFD 20, which includes acentral processing unit (CPU) 931, and various elements connected to theCPU 931 by an internal bus 932. The CPU 931 services multiple taskswhile monitoring the state of the MFD 20. In particular, the CPU 931performs a number of program instructions for the browser 25. Theelements connected to the CPU 931 include a read only memory (ROM) 933,a random access memory (RAM) 934, a hard disk drive (HDD) 935, a floppydisk drive (FDD) 936 capable of receiving a floppy disk 907, acommunication interface (I/F) 938, and a modem unit 939. In addition, acontrol panel 937, a scanner unit 940, a printer unit 941, and an imageprocessing device 942 can be connected to the CPU 931 by the bus 932.Both the I/F 938 and the modem unit 939 are connected to a communicationnetwork 100.

In a preferred embodiment, the program code instructions for the MFD 20and for the browser 25 are stored on the HDD 935 via an IC card.Advantageously, an IC card can be used to upgrade the firmware for theMFD. Alternatively, the program code instructions can be stored on thefloppy 907 so that the program code instructions may be read by the FDD936, transferred to the RAM 934 and executed by the CPU 931 to carry outthe instructions. These instructions can be the instructions to performthe MFD's functions and the browser 25's functions described above. Inparticular, these instructions permit the browser 25 to interact withthe document manger 40 and permit the MFD 20 to control its controlpanel 937 and its image processing units of the MFD 20.

During a start-up of the MFD 20, the program code instructions may beread by the CPU 931, transferred to the RAM and executed by the CPU 931.Alternatively, the program code instructions may be loaded to the ROM933. It is therefore understood that in the present invention any of thefloppy disk 907, the HHD 935, the RAM 934, and the ROM 933 correspond toa computer readable storage medium capable of storing program codeinstructions. Other devices and medium that can store the instructionsaccording to the present invention include for example magnetic disks,optical disks including DVDs, magneto-optical disks such as MOS, andsemiconductor memory cards such as PC cards.

In a preferred embodiment, the control panel 937 includes a displayscreen that displays information allowing the user of the MFD 20 tointeract with the document manager 40,such as screens 300-600 shown inFIGS. 5-8. The display screen can be a liquid crystal display (LCD), aplasma display device, or a cathode ray tube (CRT) display. The displayscreen does not have to be integral with, or embedded in, the controlpanel 937, but may simply be coupled to the control panel 937 by eithera wire or a wireless connection. The control panel 937 may include keysfor inputting information or requesting various operations.Alternatively, the control panel 937 and the display screen may beoperated by a keyboard, a mouse, a remote control, touching the displayscreen, voice recognition, or eye-movement tracking, or a combinationthereof.

The mechanisms and processes set forth in the present description may beimplemented using a conventional general purpose microprocessor(s)programmed according to the teachings of the present specification, aswill be appreciated to those skilled in the relevant arts. Appropriatesoftware coding can readily be prepared by skilled programmers based onthe teachings of the present disclosure, as will also be apparent tothose skilled in the software art. In particular, the computer programproduct for the browser functions, and for authenticating, routing, andmanaging scanned documents according to the present invention can bewritten in a number of computer languages including but not limited toC, C++, Fortran, and Basic, as would be recognized by those of ordinaryskill in the art. The invention may also be implemented by thepreparation of applications specific integrated circuits or byinterconnecting an appropriate network of conventional componentcircuits, as will be readily apparent to those skilled in the art.

The present invention thus also includes a computer-based product thatmay be hosted on a storage medium and include instructions that can beused to program a computer to perform the browser functions and thedocument management functions discussed above in accordance with thepresent invention. This storage medium can include, but is not limitedto, any type of disk including floppy disks, optical disks, CD-ROM,magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, Flash Memory,Magnetic or Optical Cards, or any type of media suitable for storingelectronic instructions.

Additional Benefits of the Present Invention

Historically, business applications ran on mainframe computers and usersexecuted operations from terminal consoles by sending instructioncommands. The terminal consoles had no computing power other thandisplaying data stream sent back from the mainframe computer which ranthe actual applications. As LAN (Local Area Network) became available,the Client-Server architecture was introduced. The Client-Serverarchitecture utilizes the client computer's computing power to offloadthe mainframe from data processing, resulting in a more efficient use ofthe resources and better overall performance.

This Client-Server technology introduced a new problem however. Each andevery computer needs to have an application program installed.Installation upgrades, and maintenance of the client require a lot oftime and human support, which increase operation cost. Furthermore, thisapproach lacks flexibility because different versions of applications onclients and servers should match.

Once introduced, the web browser was well accepted because it not onlysolves the problems of the Client-Server architecture but it also allowsthe user to maintain the benefit of distributed computing. Specifically,the web browser eliminates the need for client program maintenancebecause application programs and/or web pages are loaded dynamically atthe time the user accesses the web site. The user is guaranteed to havethe latest version of the application. As a result, PCs no longer needto have application programs installed manually and permanently on theirlocal hard disk. This is why a PC web browser is sometimes referred toas “thin client technology;” it is free from relatively bulkyapplication programs.

The MFD browser according to the present invention provides the benefitsof thin client technology to MFDs because it does not need manualprogram installation or program upgrade but still guarantees the latestand/or only appropriate software loaded from a web site. Once the MFDbrowser is incorporated in the MFD, a web server can identify thecapabilities of the MFD and dynamically download and run selectedprograms by a pre-defined criterion. This criterion can be used to rundifferent types of applications by department, e.g. a patent search anda print program for a legal department or a resume managementapplication for a human resources department. Advantageously, thepresent invention can be incorporated into the system and method formanaging documents disclosed in co-pending Ser. No. 09/795,438, theentire content of which is hereby incorporated by reference.

Obviously, numerous additional modifications and variations of thepresent invention are possible in light of the above teachings. It istherefore to be understood that within the scope of the appended claimsthe present invention may be practiced otherwise than as specificallydescribed herein.

1. A method for managing image processing apparatus, comprising thesteps of: providing a request for an image processing apparatus;processing said request so as to generate a command information;transmitting said command information to a computer using a network;receiving a response information from said computer, wherein saidresponse information is generated by processing in said computer; andcontrolling said image processing apparatus based on said responseinformation.
 2. The method of claim 1, where said controlling comprisesgenerating an image for an LCD panel of said image processing apparatus.3. The method of claim 1, wherein said providing step comprisesproviding text information by a user, and further comprisingtransmitting said text information to said computer.
 4. The method ofclaim 3, wherein said text information is a user password.
 5. The methodof claim 1, further comprising: processing image information with saidimage processing apparatus; and transmitting said image information tosaid computer.
 6. The method of claim 5, wherein said image informationcomprises a scanned document.
 7. The method of claim 1, said responseinformation comprises a control information for said image processingapparatus.
 8. The method of claim 7, wherein said control informationcomprises a user authentication.
 9. An image processing system,comprising: an image processing apparatus configured to receive arequest for an image processing operation; a processor, of the imageprocessing apparatus, configured to process said request so as togenerate a command information; a first network interface, of the imageprocessing apparatus, configured to transmit said command information toa computer using a network; the computer configured to generate responseinformation based on the command information received from the imageprocessing apparatus; a second network interface, at the computer,configured to exchange the response information with the informationprocessing apparatus; and a controller, of the image processing device,configured to control said image processing apparatus based on saidresponse information.
 10. The system of claim 1, wherein said controlleris configured to generate an image for an LCD panel of said imageprocessing apparatus.
 11. The system of claim 1, wherein said request istext information provided by a user, which is transmitted via the firstnetwork interface to said computer.
 12. The system of claim 3, whereinsaid text information is a user password.
 13. The system of claim 1,wherein the image processing device is configured to process imageinformation; and the first user interface is configured to transmit saidimage information to said computer.
 14. The system of claim 5, whereinsaid image information comprises a scanned document.
 15. The system ofclaim 1, wherein said response information comprises a controlinformation for said image processing apparatus.
 16. The system of claim7, wherein said control information comprises a user authentication.